Data Import - supported Files Formats

Import TPTBIN files

TPTBIN is TPT's own file format and offers:

Complete information about sampled signals.
Complete information about parameters.
Complete information about all inputs and outputs.
Highly flexible curves and maps integration.
Highly compressed file structure.

Import MAT files

TPT can read several types of signals contained in a MAT file type. TPT can also import regular sampled signals.

Import regular sampled signals

The MAT file must met the following prerequisites:

It must contain uniformly sampled signal-vector(s).
It must contain the scalar variable StepSize , representing the sample time in [s].

Example
The following m-script results in two signals, named foo and bar: StepSize = 0.01; foo = 1:10; bar = 1:2:19; save regular_signals StepSize foo bar Example of regular sampled signals

Import structure containing y and t

Each signal needs to be a structure.
Must include the array <struct>.t, containing the time axis.
Must include the array <struct>.y, containing the signal data.
The name of the structure will be the imported signal name.
Signal type is determined through the MATLAB-data type of the stored values.

Example
The following m-script results in two signals foo and bar: foo.t = 0:0.01:0.09; foo.y = 1:10; bar.t = 0:0.01:0.09; bar.y = 1:2:20; save ty_struct foo bar

Import signal matrix

Contains a matrix <signals-x-samples>.
First row contains the time axis.

Example
The following m-script results in two signals `matrixsignals_1` and `matrixsignals_2`: matrixsignals =[0:0.01:0.09; 1:10; 1:2:20] save matrix_signals matrixsignals

Importing signal structure

Signal needs to be a structure.
Must include the array <struct>.t, containing the time axis.
Every signal is defined as an array <struct>.<signalname>.
Signal type is determined through the MATLAB-data type of the stored values.

Example
The following m-script results in two signals: `foo` and `bar`: signalstruct.t = 0:0.01:0.09; signalstruct.foo = 1:10; signalstruct.bar = 1:2:20; save struct_signals signalstruct

Import CSV files

A valid CSV file must have:

A first column (time) to define the time values
At least one signal column (signal name) to define the signal values

Each column must be separated by a semicolon ";".

Values for structured signals must be separated by a space " ".

Example
time;signal_1;signal_2 1;0;[1 2] 2;1;[6 7] 3;2;[7 8] 4;3;[8 9] Import CSV

Import XLS and XLSX files

TPT can read signal data from XLS and XLSX (Excel Workbook) files.

The strict XLSX file format (Strict Open XML Spreadsheat) is not supported.

The first row must contain the signal names. The first column must contain the time axis. Therefore the first entry (A1) must be named "Time".

Example XLSX file

The XLSX file either needs to contain only one worksheet or in case of several worksheets the one containing the test data needs to be named "testdata".

Import DCM

You may find that parameters often have prefixes or postfixes when you import data from a DCM file. TPT uses the pattern (\S*_)?(${PARAMETER})(_\S*)? to search for matching parameters in a file. That means, any prefix or postfix to the parameter is ignored.

If you need to change this pattern, go to Options|Preferences|Variables. Click Create a new Variable, type DCM_NAME_MATCH_PATTERN as the variable name and specify your custom filter pattern in the Value field.

The variable can be declared either as global or local variable, see Global Variables or Project-specific Variables.

Pattern specified in the 'TPT Tool Preferences dialog'

This pattern must be formed with regular expressions, see Common Regular Expressions.

Import MDF

TPT can import comment information from MDF3 as strings.
TPT imports MDF4 event blocks as string variables. Events are represented as string-variables in TPT. These string-variables are also displayed in the Signal Viewer.
Half precision float data types (16 bit) can be imported from MDF files of version 4.20. During the import, these data types are converted to float data types (32 bit).

Data Import - supported File Formats